CSC_DISTRIBUTE
==============

   Usually, you will use custom classes only for your own applications.
In this case, you won't need to care about the tag values used for your
private attributes and methods. The only thing you should consider is
that all standard MUI classes use values betwenn 0x80420000 and
0x8042ffff for their tags. To avoid conflicts, all you have to do is
make your tags start with anything but 0x8042.

   However, if you start distributing your classes to make other people
benefit from your work and help them in writing better MUI applications,
things get a bit more complicated. MUI will get confused if two or more
classes start using some equal tag values. To avoid these problems, I
suggest to use your MUI serial number together with the TAG_USER bit as
upper word for your tag items. Thus, if your serial number is e.g. 123,
all your tag items would look like

     #define MUIA_Myclass_Foobar     (TAG_USER | (123<<16) | 0x0000)
     #define MUIA_Myclass_Barfoo     (TAG_USER | (123<<16) | 0x0001)
     #define MUIA_Myclass_Deadbeaf   (TAG_USER | (123<<16) | 0x0002)
     #define MUIM_Myclass_Doit       (TAG_USER | (123<<16) | 0x0003)
     #define MUIM_Myclass_Doit2      (TAG_USER | (123<<16) | 0x0004)
     
     #define MUIA_Myotherclass_Attr1 (TAG_USER | (123<<16) | 0x0010)
     #define MUIA_Myotherclass_Attr2 (TAG_USER | (123<<16) | 0x0011)
     #define MUIA_Myotherclass_Attr3 (TAG_USER | (123<<16) | 0x0012)
     #define MUIA_Myotherclass_Attr4 (TAG_USER | (123<<16) | 0x0013)

   If you aren't registered and don't yet have a serial number, no
problem... just register *now*! ;-)